Stack entry overwrite protection

ABSTRACT

A computer processor receives a plurality of execution items corresponding to a computer process. The computer processor allocates a first memory portion corresponding to a first stack, wherein the first stack corresponds to a first class of execution items. The computer processor allocates a second memory portion corresponding to a second stack, wherein the second stack corresponds to a second class of execution items. The computer processor identifies a first execution item of the plurality of execution items and determining a class corresponding to the first execution item.

FIELD OF THE INVENTION

The present invention relates generally to the field of data security,and more particularly to stack entry overwrite protection.

BACKGROUND OF THE INVENTION

Many programming languages employ a stack to manage data during programexecution time. Such languages include languages like C, C++, and Java®(note: the term(s) “Java” and the like may be subject to trademarkrights in various jurisdictions throughout the world and are used hereonly in reference to the products or services properly denominated bythe marks to the extent that such trademark rights may exist). A stackis used to store and manage data associated with subroutine calls, whichmay also be called procedures, functions, or methods, depending on theprogramming language. In response to such a call, the stack storesinformation. For example, the stack can store a return address, which isa memory address at which to resume program execution in response tocompletion of the call. The stack can store data which is extendable ornon-extendable in length.

A stack overflow is a computer security attack which occurs when aprogram writes to a memory address on the program's stack outside of theintended data structure. A stack overflow attack can involve writingdata beyond the portion of the stack in which an extendable length datavalue is stored, thus overwriting adjacent data. Such an attack canfunction to overwrite the function return address with a pointer toattacker-controlled data or code.

SUMMARY

Embodiments of the present invention provide a method, computer programproduct, and system for executing a computer process. A computerprocessor receives a plurality of execution items corresponding to thecomputer process. The computer processor allocates a first memoryportion corresponding to a first stack, wherein the first stackcorresponds to a first class of execution items. The computer processorallocates a second memory portion corresponding to a second stack,wherein the second stack corresponds to a second class of executionitems. The computer processor identifies a first execution item of theplurality of execution items and determines a class corresponding to thefirst execution item.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a computingenvironment, in accordance with an embodiment of the present invention.

FIG. 2 is a flowchart depicting operational steps of a program module,on a computing system 102 within the computing environment of FIG. 1,for executing a process with stack overflow protection, in accordancewith an embodiment of the present invention.

FIG. 3 is a flowchart depicting the operational steps of a programmodule executing a command with stack overflow protection, in accordancewith an embodiment of the present invention.

FIG. 4 depicts a block diagram of components of the computing systemexecuting the program module, in accordance with an embodiment of thepresent invention.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentdisclosure may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present disclosure may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.), or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present disclosure may take the form of acomputer program product embodied in one or more computer-readablemedium(s) having computer-readable program code/instructions embodiedthereon.

Any combination of computer-readable media may be utilized.Computer-readable media may be a computer-readable signal medium or acomputer-readable storage medium. A computer-readable storage medium maybe, for example, but not limited to, an electronic, magnetic, optical,or semiconductor system, apparatus, or device, or any suitablecombination of the foregoing. More specific examples (a non-exhaustivelist) of a computer-readable storage medium would include the following:a portable computer diskette, a hard disk, a random access memory (RAM),a read-only memory (ROM), an erasable programmable read-only memory(EPROM or Flash memory), a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer-readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device. The term“computer-readable storage media” does not include computer-readablesignal media.

A computer-readable signal medium may include a propagated data signalwith computer-readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer-readable signal medium may be any computer-readable medium thatis not a computer-readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium may be transmittedusing any appropriate medium, including, but not limited to, wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent disclosure may be written in any combination of one or moreprogramming languages, including an object-oriented programming languagesuch as Java®, Smalltalk® (note: the term(s) “Java”, “Smalltalk” and thelike may be subject to trademark rights in various jurisdictionsthroughout the world and are used here only in reference to the productsor services properly denominated by the marks to the extent that suchtrademark rights may exist), C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on a user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computer,or entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).

Aspects of the present disclosure are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, a specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable medium that can direct a computer, other programmabledata processing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus, or other devices to produce acomputer-implemented process such that the instructions which execute onthe computer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The present disclosure will now be described in detail with reference tothe Figures.

FIG. 1 is a functional block diagram illustrating a computingenvironment, generally designated 100, in accordance with an embodimentof the present disclosure.

Computing environment 100 includes computing system 102, which isconnected to network 120. Computing system 102 may be a laptop computer,a tablet computer, a netbook computer, a personal computer (PC), adesktop computer, a personal digital assistant (PDA), a smart phone, orany programmable electronic device capable of communicating via network120. In other embodiments, computing system 102 may represent a servercomputing system utilizing multiple computers as a server system, suchas in a cloud computing environment. In another embodiment, computingsystem 102 represents a computing system utilizing clustered computersand components to act as a single pool of seamless resources. Ingeneral, computing system 102 is representative of any programmableelectronic device or combination of programmable electronic devicescapable of executing machine-readable program instructions andcommunicating with other computing devices via a network.

Computing system 102 may include internal and external hardwarecomponents, as depicted and described in further detail with respect toFIG. 4.

Network 120 can be, for example, a local area network (LAN), a wide areanetwork (WAN) such as the Internet, or a combination of the two, and caninclude wired, wireless, or fiber optic connections. In general, network120 can be any combination of connections and protocols that willsupport communications with server computer 102.

Embodiments of the present disclosure provide for initializing andmanaging multiple stacks, wherein the stacks correspond to at least oneexecutable process. Further, each computer process can perform afunction call, each of which may result in the addition of one or moreexecutable items to a stack. A stack is a data structure that ordersexecutable items of executable processes (e.g., subroutines). Executableitems include memory addresses (e.g., return addresses), arguments,variables, or other data structures. Each stack is associated with atleast one computer processor which manages the stack and executessubroutines using the executable items. Embodiments of the presentdisclosure further provide for classifying the executable items into aclass corresponding to at least one of the stacks.

Program module 104 operates to protect against stack overflow events. Inone embodiment, program module 104 protects against stack overflow byinitializing and maintaining general stack 106 for extendable executionitems and secure stack 110 for non-extendable execution items. Inanother embodiment, general stack 106 may include extendable andnon-extendable execution items. In one embodiment, a non-extendableexecution item comprises a data structure with a fixed size. An exampleof a non-extendable execution item is a return address, which identifiesa memory address at which to resume operation of the program aftercompletion of a calling function. Another example of a non-extendableexecution item is an integer in the C++ programming language, which, inone implementation, is fixed at 4 bytes in size. In one embodiment, anextendable execution item comprises a data structure with a variablesize. Examples of an extendable execution item include a vector, anarray, another dynamically-sized data structure, or a data structurecomprising a plurality of data elements accessed by an index.

Computing system 102 includes program module 104, general stack 106,general access key 108, secure stack 110, and secure access key 112. Incomputing environment 100, general stack 106 is associated with generalaccess key 108 and secure stack 110 is associated with secure access key112. In one embodiment, general access key 108 and secure access key 112each represent a unique authentication key comprising a series ofcharacters.

Program module 104 executes a command corresponding to general stack 106or secure stack 110. In one embodiment, the command includes user inputreceived from a client device. In one embodiment, the command comprisesan access key, which is an authentication key comprising a series ofcharacters. The access key may match general access key 108 or secureaccess key 112. Program module 104 validates the access key of thecommand in order to authenticate access to general stack 106 and securestack 110.

In one embodiment, program module 104 resides on computing system 102.In other embodiments, program module 104 may reside on another computingsystem or another computing device, provided that program module 104 isaccessible to, and can access, general stack 106, general access key108, secure stack 110, and secure access key 112. Program module 104 isdiscussed in more detail in connection with FIGS. 2 and 3.

In one embodiment, general stack 106, general access key 108, securestack 110, and secure access key 112 each reside on computing system102. In other embodiments, general stack 106, general access key 108,secure stack 110, and secure access key 112 each reside on anothercomputing system or another computing device, provided that each isaccessible by program module 104. In another embodiment, general accesskey 108 and secure access key 112 reside in a repository, which may beprotected by additional layers of authentication or access control.General stack 106, general access key 108, secure stack 110, and secureaccess key 112 are each discussed in more detail in connection withFIGS. 2 and 3.

FIG. 2 is a flowchart depicting operational steps of program module 104,on computing system 102 within the computing environment of FIG. 1, forprogram execution with stack overflow protection, in accordance with anembodiment of the present disclosure.

In step 202, program module 104 allocates memory. Allocating memorymeans reserving a portion of a computer memory to store a particulardata structure. In one embodiment, program module 104 allocates memoryfor general stack 106 and secure stack 110. For example, program module104 may allocate memory in a first memory location for general stack 106and in a second memory location for secure stack 110. In one example,the first and second memory locations are non-adjacent. In an alternateexample, the first and second memory locations are adjacent and anyadditional allocations to expand the allocations at the first and secondmemory locations occur in opposite directions. In one embodiment,program module 104 stores a reference to the memory locations of generalstack 106 and secure stack 110.

In step 204, program module 104 determines general access key 108 andsecure access key 112. In one embodiment, program module 104 determinesgeneral access key 108 and secure access key 112 by generating anauthentication key for each. For example, program module 104 maydetermine each of general access key 108 and secure access key 112 bygenerating a series of random characters. In another embodiment, programmodule 104 receives each of general access key 108 and secure access key112, for example as user input from a client device. In yet anotherembodiment, general access key 108 and secure access key 112 are eachpre-determined.

In step 206, program module 104 identifies an execution item. In oneembodiment, program module 104 identifies an execution item byclassifying the execution item. For example, program module 104 mayclassify the execution item into an extendable class or a non-extendableclass. The execution item is associated with a function call. A singlefunction call may result in the generation of one or more executionitems. In one embodiment, the execution item comprises a return address.In another embodiment, the execution item comprises one or more datastructures. For example, the execution item may comprise a parameter orargument of the function call and/or a return value of the functioncall.

In decision 208, program module 104 determines whether the executionitem is extendable. In one embodiment, program module 104 determineswhether the execution item is extendable based on whether the executionitem comprises a data structure of variable size. In another embodiment,program module 104 determines whether the execution item is extendablebased on whether the execution item is classified into an extendableclass. For example, a vector in the C programming language and a stringin the C++ programming language are each data structures of variablesize. As another example, the execution item may comprise a datastructure which includes a second data structure of variable size, suchas a user-defined data structure. If program module 104 determines thatthe execution item is extendable (decision 208, YES branch), thenprogram module 104 stores the execution item to the general stack (step210). If program module 104 determines that the execution item is notextendable (decision 208, NO branch), then program module 104 stores theexecution item to the secure stack (step 212). In some embodiments,program module 104 performs step 206, decision 208, and step 210 or 212for each execution item.

FIG. 3 is a flowchart depicting an illustrative embodiment ofoperational steps of program module 104 executing a command with stackoverflow protection, in accordance with an embodiment of the presentdisclosure.

Initially, program module 104 performs the operations depicted in FIG.2. Thus, general stack 106 and secure stack 110 are allocated, generalstack 106 is associated with general access key 108, and secure stack110 is associated with secure access key 112.

In step 302, program module 104 receives a command. The commandidentifies an operation and a stack (e.g., general stack 108 or securestack 112). For example, the command may identify a write operation, inwhich case the command comprises data to be written. As another example,the command may identify a read operation, in which case the commandcomprises a destination (e.g., a memory address) to which to write therequested data. In another embodiment, the command further comprises acommand key. In yet another embodiment, the command further identifies aportion of the associated stack on which to perform the operation, suchas by identifying a memory offset relative to the memory address atwhich the identified stack is stored.

In decision 306, program module 104 determines whether the commandidentifies secure stack 112. In one embodiment, the command identifieseither general stack 108 or secure stack 112. If program module 104determines that the command does not identify the secure stack (decision306, NO branch), then program module 104 processes the command viageneral stack path 308. If program module 104 determines that thecommand identifies the secure stack (decision 306, YES branch), thenprogram module 104 processes the command via secure stack path 316.

General stack path 308 comprises step 310, decision 312, and step 314.In step 310, program module 104 compares the command key to generalaccess key 108. In various embodiments, the operations of general stackpath 308 may be performed entirely by hardware, entirely by software, orby a combination of software and hardware.

In decision 312, program module 104 determines whether the command keymatches general access key 108. If program module 104 determines thatthe command key does not match general access key 108 (decision 312, NObranch), then program module 104 encounters an error (step 326,discussed below). If program module 104 determines that the command keymatches general access key 108 (decision 312, YES branch), then programmodule 104 executes the command (step 314).

Secure stack path 316 comprises step 318, decision 320, and step 322. Instep 318, program module 104 compares the command key to secure accesskey 112. In various embodiments, the operations of general stack path308 may be performed entirely by hardware, entirely by software, or by acombination of software and hardware.

In decision 320, program module 104 determines whether the command keymatches secure access key 112. If program module 104 determines that thecommand key does not match secure access key 112 (decision 320, NObranch), then program module 104 encounters an error (step 326,discussed below). If program module 104 determines that the command keymatches the secure access key (decision 320, YES branch), then programmodule 104 executes the command (step 322).

In step 326, program module 104 encounters an error. In one embodiment,program module 104 generates an exception in response to encountering anerror. In another embodiment, program module 104 ceases operation inresponse to encountering an error. For example, program module 104 mayterminate itself in an event which may be referred to as a programcrash. In yet another embodiment, program module 104 returns an errormessage to a client device. For example, the error message may identifythe command, the stack associated with the command, and the command key.

Some embodiments of the present disclosure are implemented withoutgeneral access key 108 or secure access key 112. In such embodiments,program module 104 does not perform the operations of steps 204 of FIG.2 or steps 310, 318 and decisions 312 and 320 of FIG. 3.

FIG. 4 depicts a block diagram of components of computing system 102 inaccordance with an illustrative embodiment of the present disclosure. Itshould be appreciated that FIG. 4 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

Computing system 102 includes communications fabric 402, which providescommunications between computer processor(s) 404, memory 406, persistentstorage 408, communications unit 410, and input/output (I/O)interface(s) 412. Communications fabric 402 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as microprocessors, communications and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, communications fabric402 can be implemented with one or more buses.

Memory 406 and persistent storage 408 are computer-readable storagemedia. In this embodiment, memory 406 includes random access memory(RAM) 414 and cache memory 416. In general, memory 406 can include anysuitable volatile or non-volatile computer-readable storage media.

Program module 104, general stack 106, secure stack 110, general accesskey 108, and secure access key 112 are stored in persistent storage 408for execution and/or access by one or more of the respective computerprocessor(s) 404 via one or more memories of memory 406. In thisembodiment, persistent storage 408 includes a magnetic hard disk drive.Alternatively, or in addition to a magnetic hard disk drive, persistentstorage 408 can include a solid-state hard drive, a semiconductorstorage device, read-only memory (ROM), erasable programmable read-onlymemory (EPROM), flash memory, or any other computer-readable storagemedia that is capable of storing program instructions or digitalinformation.

The media used by persistent storage 408 may also be removable. Forexample, a removable hard drive may be used for persistent storage 408.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer-readable storage medium that is also part of persistent storage408.

Communications unit 410, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 410 includes one or more network interface cards.Communications unit 410 may provide communications through the use ofeither or both physical and wireless communications links. Programmodule 104, general stack 106, secure stack 110, general access key 108,and secure access key 112 may be downloaded to persistent storage 408through communications unit 410.

I/O interface(s) 412 allows for input and output of data with otherdevices that may be connected to computing system 102. For example, I/Ointerface(s) 412 may provide a connection to external device(s) 418 suchas a keyboard, a keypad, a touch screen, and/or some other suitableinput device. External device(s) 418 can also include portablecomputer-readable storage media such as, for example, thumb drives,portable optical or magnetic disks, and memory cards. Software and dataused to practice embodiments of the present disclosure, e.g., programmodule 104, general stack 106, secure stack 110, general access key 108,and secure access key 112, can be stored on such portablecomputer-readable storage media and can be loaded onto persistentstorage 408 via I/O interface(s) 412. I/O interface(s) 412 also connectto a display 420.

Display 420 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of thedisclosure. However, it should be appreciated that any particularprogram nomenclature herein is used merely for convenience, and thus thedisclosure should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the Figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is: 1-8. (canceled)
 9. A computer program product forexecuting a computer process, the computer program product comprising:one or more computer-readable storage media and program instructionsstored on the one or more computer-readable storage media, the programinstructions comprising program instructions to: receive a plurality ofexecution items corresponding to the computer process; and allocate aplurality of memory portions, wherein the plurality of memory portionsincludes (i) a first memory portion corresponding to a first stack, thefirst stack corresponding to a first class of execution items and (ii) asecond memory portion corresponding to a second stack, the second stackcorresponding to a second class of execution items.
 10. The computerprogram of claim 9, wherein the first class corresponds to extendabledata types and the second class corresponds to non-extendable datatypes.
 11. The computer program of claim 10, further comprising programinstructions to: identify a first execution item of the plurality ofexecution items; determine that the first execution item corresponds tothe first class; and store the first execution item to the first stack.12. The computer program of claim 10, further comprising programinstructions to: identify a first execution item of the plurality ofexecution items; determine that the first execution item corresponds tothe second class; and store the first execution item to the secondstack.
 13. The computer program of claim 9, wherein each of the firstmemory portion and the second memory portion is associated with anaccess key.
 14. The computer program of claim 13, further comprisingprogram instructions to: store the first execution item to the firststack based, at least in part, on a determination that (i) a firstexecution item of the plurality of execution items corresponds to thefirst class and (ii) the first execution item includes a key thatcorresponds to the access key of the first memory portion.
 15. Acomputer system for executing a computer process, the computer systemcomprising: one or more computer processors; one or morecomputer-readable storage media; program instructions stored on thecomputer-readable storage media for execution by at least one of the oneor more processors, the program instructions comprising programinstructions to: receive a plurality of execution items corresponding tothe computer process; and allocate a plurality of memory portions,wherein the plurality of memory portions includes (i) a first memoryportion corresponding to a first stack, the first stack corresponding toa first class of execution items and (ii) a second memory portioncorresponding to a second stack, the second stack corresponding to asecond class of execution items.
 16. The computer system of claim 15,wherein the first class corresponds to extendable data types and thesecond class corresponds to non-extendable data types.
 17. The computersystem of claim 16, further comprising program instructions to: identifya first execution item of the plurality of execution items; determinethat the first execution item corresponds to the first class; and storethe first execution item to the first stack.
 18. The computer system ofclaim 16, further comprising program instructions to: identify a firstexecution item of the plurality of execution items; determine that thefirst execution item corresponds to the second class; and store thefirst execution item to the second stack.
 19. The computer system ofclaim 15, wherein each of the first memory portion and the second memoryportion is associated with an access key.
 20. The computer system ofclaim 19, further comprising program instructions to store the firstexecution item to the first stack based, at least in part, on adetermination that (i) a first execution item of the plurality ofexecution items corresponds to the first class and (ii) the firstexecution item includes a key that corresponds to the access key of thefirst memory portion.